Automated deployment of protection agents to devices connected to a distributed computer network

ABSTRACT

Network traffic is monitored to detect attempted inter-network communications, including attempts by devices internal to the network to communicate with resources external to the network and attempts by devices external to the network to establish VPN sessions with resources internal to the network. Upon detecting an attempted inter-network communication, the device responsible for initiating such communication is identified. Then, it is determined whether the identified device is running a valid protection agent. If so, the attempted inter-network communication is permitted. If not, the attempted inter-network communication is blocked in compliance with a network security policy and the identified device is prompted to download and install a protection agent from a designated storage location, or to activate a previously installed protection device. The prompt may include a hyperlink for initiating download of the protection agent.

RELATED APPLICATIONS

This application is a continuation application of U.S. patent application Ser. No. 11/517,165, filed on Sep. 7, 2006, entitled “Automated Deployment of Protection Agents to Devices Connected to a Distributed Computer Network,”, which claims the benefit of U.S. Provisional Patent Application No. 60/714,605, entitled “Systems and Methods for Downloading Protection Agents in a Distributed Computer Network,” which was filed on Sep. 7, 2005. The entire contents of each patent application identified above are hereby incorporated herein by reference.

TECHNICAL FIELD

The present invention relates generally to computer network security. More specifically, the present invention relates to the deployment of protection agents to workstations, clients, servers and other devices connected to a distributed computer network.

BACKGROUND OF THE INVENTION

Private computer networks are often interconnected to other networks, such as the Internet, and are therefore susceptible to intrusion. For this reason, many private networks are protected by some type of intrusion prevention system. An intrusion prevention system can be generally described as hardware and/or software for exercising access control to protect computers and other network resources from exploitation. There are several different types of intrusion prevention systems, including network intrusion prevention systems (“network IPS”) and host-based intrusion prevention systems (“host-based IPS”).

Network IPS are typically hardware and software platforms designed to analyze, detect and report on security related events. Network IPS inspect traffic and, based on their configuration or security policy, can drop malicious traffic. Network IPS are designed sit inline with network traffic flows and prevent attacks in real-time. In addition, most network IPS have the ability to decode certain communication protocols like HTTP, FTP, and SMTP, which provides greater awareness. Some network IPS, such as the Proventia® Network Multi-Function Security (also referred to as “Proventia® M”) by Internet Security Systems, Inc. of Atlanta Ga. (“ISS”), perform multiple network security functions, including firewall, VPN, anti-virus, Web filtering and anti-spam protection.

Host-based IPS run on a host, such as a client, workstation, server or other device, where packets have been decrypted and file-access and registry-access can be monitored granularly and accurately. As an example, Proventia® Desktop Endpoint Security by ISS is a host-based IPS that is designed to preemptively protect desktop workstations against viruses, worms and improper activity, while keeping operations running and enforcing system compliance. As another example, Proventia® Server Intrusion Prevention System by ISS is a host-based IPS that is designed to proactively stop threats which could compromise valuable and critical applications and assets residing on a network server. Host-based IPS are sometimes referred to as “desktop agents” or “protection agents” because they may be deployed to various network devices and controlled from a centralized management console. In some cases, a network-IPS may also function as a management console for protection agents deployed to devices within the same network.

Devices connected to a private network may be internal to the network (i.e., behind the network firewall) or external to the network (i.e., beyond the network firewall, but in communication with an internal network resource by way of a virtual private network session, etc.) In an optimal scenario, a protection agent will be deployed to each device connected to a private network. In this way, each device connected to the private network will be individually protected against unauthorized network communications, such as intrusions and virus infections. However, the configuration of a distributed computer network can change rapidly over time as servers, workstations, clients and other devices and resources are added, replaced, relocated and repurposed. Therefore, ensuring that protection agents are deployed to all relevant network devices can be cumbersome and time-consuming for a network administrator. Accordingly, there is a need in the art for an efficient and automated method for deploying protection agents to devices connected to a distributed computer network.

SUMMARY OF THE INVENTION

The present invention satisfies the above-described need by providing systems and methods for automating the deployment of protection agents to devices connected to a distributed network. Generally described, the present invention involves monitoring network traffic and detecting attempted inter-network communications. Attempted inter-network communications can include attempts by devices internal to the distributed network to communicate with resources external to the distributed network and attempts by devices external to the distributed network to establish virtual private network sessions with resources internal to the distributed network. Attempts by devices internal to the distributed network to communicate with resources external to the distributed network can be detected by identifying network traffic employing HTTP or HTTPS protocols or network traffic on one or more of port 80 and port 443.

In response to detecting an attempted inter-network communication, the device responsible for initiating such communication is identified. Then, a determination is made as to whether the identified device is running a valid protection agent. If so, the attempted inter-network communication is permitted. If not, the attempted inter-network communication is blocked and the identified device is prompted to download and install a protection agent from a designated storage location, or to activate a previously installed protection device.

Registration information generated by protection agents running on devices connected to the distributed network may be collected and stored. Determining that the identified device is not running a valid protection agent may involve determining that none of the stored registration information corresponds to the identified device. Determining that the identified device is not running a valid protection agent may also involve determining that none of the registration information stored in within a specified time interval corresponds to the identified device. Prompting the identified device to download and install a protection agent may involve providing a hyperlink that, when activated, will initiate the download of the protection agent from the designated storage location, which may be an intrusion prevention system, a network server, or the like.

These and other aspects, features and embodiments of the present invention will become apparent to those skilled in the art upon consideration of the following detailed description of illustrated embodiments exemplifying the best mode for carrying out the invention as presently perceived.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a suitable computer network environment 100 for implementing certain exemplary embodiments of the present invention.

FIG. 2 is a process flow diagram illustrating an exemplary method for deploying protection agents to devices connected to a distributed computer network, in accordance with certain exemplary embodiments of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The present invention provides systems and methods for deploying protection agents to devices connected to a distributed computer network. The following description of exemplary embodiments of the invention will refer to the attached drawings, in which like numerals indicate like elements throughout the several figures. FIG. 1 is a block diagram illustrating a suitable computer network environment 100 for implementing exemplary embodiments of the present invention. The exemplary computer network environment 100 includes at least two distributed networks, including a private network 105 and a public network 110. The private network 105 may be a local area network (“LAN”), a wide area network (“WAN”), a combination thereof, or any other intranet configuration. The public network 110 may be the Internet or any other publicly accessible computer network.

A private network 105 may include one or more endpoint devices, such as servers 120, clients 125 and other computer or electronic devices. Such devices may be connected to the private network 105 through a network interface card, modem or other suitable means for establishing and receiving network communications. A client 125 may be a desktop computer 125 a, a laptop computer 125 b, a handheld computer 125 c and the like. Remote clients 125 d and other devices (e.g., mobile phones) may communicate with the private network 105 via a virtual private network “(VPN”) 165 or other suitable secure communication protocols. As is well known in the art, a VPN 165 can be established using one or more of a variety of security measures to provide secure access to a private network 105 via a public network 110.

As is also well known in the art, a device capable of connecting to a network (e.g., a client 125, a server 120, etc.) generally includes a processor for executing computer-executable instructions, a system memory (i.e., a suitable storage medium) for storing program modules and data and a system bus that couples the system memory to the processing unit. System memory typically includes read only memory (“ROM”) and/or random access memory (“RAM”). A network device may also include a hard disk drive, a magnetic disk drive (i.e., for reading from and writing to a magnetic disk), and/or an optical disk drive (i.e., for reading from or writing to optical media, such as a CD or DVD), each of which may be connected to the system bus via an appropriate interface. Such drives and their associated computer-readable media provide nonvolatile storage for the computer system. Those skilled in the art will appreciate that other types of media readable by a computer system include magnetic cassettes, flash memory cards, zip drives, Bernoulli cartridges, and the like.

A number of program modules may be stored in the nonvolatile storage (e.g., hard disk), the system memory (e.g., RAM) and/or other computer-readable media of a network device. Typical program modules installed on and executed by a network device include a basic input/output system (“BIOS”), an operating system and one or more application program. As used herein, the term “program module” is also intended to encompass components of an application program, such as executable files, DLLs, etc., and any other computer-executable instructions that cause a processor to perform desired functions. Certain embodiments of the present invention may be implemented through one or more intrusion prevention system program modules and/or protection agent program modules that include computer-executable instructions for performing the various methods described herein.

A typical private network 105 is guarded by a firewall 115 at a gateway connection to a public network 110 or other external network. As is well known in the art, a firewall 115 is hardware and/or software for preventing communications forbidden by a security policy. Many private networks 105 are also protected by some type of intrusion prevention system 165. Like a firewall 115, an intrusion prevention system 165 is hardware and/or software for exercising access control to protect computers from exploitation. However, whereas firewalls 115 typically make access control decisions based on IP addresses or ports, intrusion prevention systems 165 make access control decisions based on application content.

In some cases, IPS functionality and firewall functionality may be combined into a single device or set of devices. Accordingly, as used herein, the term “intrusion prevention system” (or “IPS”) is meant to broadly refer to any hardware and/or software platform that performs or manages network IPS functionality and/or firewall functionality, including any associated management consoles. As is well known in the art, network IPS functionality includes the inspection and analysis of network traffic flows and the ability to detect and drop malicious traffic based on a security policy. As shown in FIG. 1, an IPS 165 may be placed beyond a firewall 115 (i.e., between the public network 110 and the firewall 115) and/or behind a firewall 115. In accordance with the present invention, an IPS 165 is also configured to manage the deployment of protection agents 170 to the clients 125, servers 120 and other devices connected to the exemplary private network 105.

An IPS 165 can be configured to monitor and analyze network traffic (sometimes referred to as “message traffic”) carried by a distributed computer network, such as the exemplary private network 105, to detect inter-network access activities being performed or requested in relation thereto. For example, an IPS 165 may be configured to monitor network traffic employing HTTP or HTTPS protocols, to thereby detect attempts by a client 125 a-c or servers 120 internal to the private network 105 to access the public network 110 or other resources external to the private network 105. In addition, or in the alternative, an IPS 165 can be configured to detect attempts to access the public network 110 or other external resources by monitoring network traffic on ports 80 and 443 generated by devices internal to the private network 105. An IPS 165 may also have access to network configuration information identifying each client 125 a-c,server 120 or other device connected to the private network 105. Accordingly, an IPS 165 is able to identify any particular device connected to the private network 105 that attempts to access the public network 110 or any other external network resource. In addition, an IPS 165 according to the present invention can be configured to drop all inter-network traffic to and from devices connected to the private network 105 that are not running a valid protection agent 170.

In certain embodiments, protection agents 170 are deployed to network devices using a “pull” model, which relies on the network devices to download protection agents 170 from the IPS 165, or another designated server, for installation onto the network devices. As an example, based on network configuration information, the IPS 165 can respond to a client's 125 a attempted web browsing activity with a prompt to install and/or activate a protection agent 170 a. If the protection agent 170 a is not already installed on the client 125 a, the user can respond to the prompt by initiating a download of the protection agent 170 a for installation on and execution by the client 125 a. In certain embodiments, the prompt issued by the IPS 165 may include a hyperlink that can be activated to initiate the download of the protection agent 170 a.

The use of a hyperlink to facilitate a download of a program module is well-known in the art and, therefore, specific implementation details are not discussed herein. Those skilled in the art will appreciate that there are many other methods and programming techniques for facilitating downloads, any of which may be employed by the present invention. Also, in certain alternate embodiments, protection agents 170 can be deployed to network devices using a “push” model. In a “push” model an IPS 165, or another designated server, is configured to deliver (or cause to be delivered) protection agents 170 to devices that do not otherwise request such delivery.

Protection agents 170 may be configured to contact the IPS 165 (or another registration device) to complete a registration operation, once installed and activated on a client 125. The registration operation, in certain embodiments, may provide the IPS 165 with information that links the registering protection agent 170 with the identity of the device on which it is installed. In other words, the registration information comprises the identity of the protection agent 170 and the identity of the corresponding network device. The registration information can be stored in a database or in another suitable storage medium functionally coupled to or accessible by the IPS 165.

Protection agents 170 may be further configured to communicate registration information to the IPS 165 (or another designated registration device) on an on-going basis, as long as they are actively running For example, the protection agents 170 may use a “heartbeat” or “polling” signal to forward registration information to the IPS 165 (or another registration device) at discrete intervals on a continuous basis. Alternatively, the protection agents 170 may forward registration information to the IPS 165 (or another registration device) at irregular, random or pseudo-random intervals. As another example, the IPS 165 (or other registration device) may be configured to query one or more network devices in order to request registration information from any protection agents 170 installed thereon.

When a network device attempts to access the Internet 110, or any other resource external to the private network 105, the IPS 165, which monitors network traffic and other operations and acts as an agent manager, determines whether the device is running a valid protection agent 170. Based on the identity of the network device, which may be determined by its network address, MAC address, or any other suitable unique identifier, the IPS 165 queries the stored registration information to determine whether a protection agent 170 has been previously registered in association with that device. In certain embodiments, the network device will be deemed to be not running a valid protection agent 170 if it is running a protection agent 170 that has not been registered within a preconfigured or configurable time interval.

If the IPS 165 determines that the network device is running a valid protection agent 170, the IPS 165 will allows the device to communicate with resources external to the private network 105. If, on the other hand, the network device is determined to not be running a valid protection agent 170, IPS 165 will take action to block some or all (depending on the security policy applied to the IPS 165) inter-network communications to and from that device. For example, it may be desirable in some cases to block all inter-network communications to and from the non-compliant device. In other cases, inter-network communications between the non-compliant device and certain trusted external resources may be permitted.

The user interface display at the network device can be used to advise the user of any blocked-access action taken by the IPS 165. For example, the IPS 165 may be configured to send prompt, in the form of a webpage or other suitable message, to a network device that is not running a valid protection agent, in response to the detection of attempted inter-network communications by that device. The prompt may advise the user that a previously installed protection agent 170 must be activated or that a protection agent 170 must be installed (e.g., by activating a hyperlink to initiate a download) and activated before communications with some or all resources external to the private network 105 will be permitted.

As is known in the art, an IPS 165 may also include functionality detecting attempts by external clients 125 d and other external devices to access the resources of the private network 105 by way of a VPN session. In certain embodiments of the present invention, an IPS 165 may be configured to identify any external device attempting to establish a VPN session and deploy protection agents 170 to that device, if necessary. For example, IPS 165, acting as an agent manager, may query the stored registration information to determine whether an external client 125 d attempting to establish a VPN session is associated with a previously registered protection agent 170 d and, if so, whether that protection agent 170 d was registered during a specified time interval. If the external client 125 d is determined to be running a valid (e.g., timely registered) protection agent 170 d, the IPS 165 allows the VPN session to continue. If, on the other hand, the external client 125 d is deemed to not be running a valid protection agent 170 d, the IPS 165 takes action to block the VPN session (or, depending on the applicable security policy, to confine it to certain activities) and may prompt the user of the external client 125 d to install (e.g., by selecting a hyperlink to initiate a download) and/or activate a protection agent 170 d.

FIG. 2 is a process flow diagram illustrating an exemplary method 200 for deploying protection agents 170 to devices connected to a distributed computer network. The exemplary method begins at starting block 201 and proceeds to step 202, where communications to and from the distributed network are monitored. Next at step 204, an attempted inter-network communication is detected. The attempted inter-network communication may be an attempt by a device internal to the distributed network to communicate with an external resource. As another example, attempted inter-network communication may be an attempt by a device external to the distributed network to establish a VPN session with an internal network resource. In response to detecting an attempted inter-network communication, the device attempting to initiate such communication is identified at step 206. As previously described, the device may be internal or external to the distributed network.

After identifying the device attempting to initiate the inter-network communication, a determination is made at step 208 as to whether the identified device is associated with a registered protection agent 170. For example, protection agents 170 running on devices connected to the distributed network may be configured to generate and provide registration information to an IPS 165 (or other designated registration device) on a periodic basis. The IPS 165 (or other registration device) may store such registration information in a database or other suitable storage medium, and may later query that registration information to determine if a registered protection agent 170 is associated with the identified device. If the identified device is associated with a registered protection agent 170, a further determination may be made at step 210 as to whether the protection agent was registered within a specified time interval. In certain embodiments, the time interval may be specified by the network administrator. Such an optional further determination can be used to ensure that the registered protection agents 170 remains actively running on the device. If the protection agent is determined at step 210 to have been registered within a specified time interval, the exemplary method 200 advances to step 212, where the attempted inter-network communication is permitted.

If it is determined at step 208 that the identified device is not associated with a registered protection agent 170, or if it is determined at step 210 that the protection agent was not registered within the specified time interval, the exemplary method 200 moves to step 214, where the attempted inter-network communication is blocked. After blocking the attempted inter-network communication, the identified device is prompted at step 216 to install and/or activate a protection agent. From either step 216 or step 212, the exemplary method 200 returns to and is repeated from step 202, where communications to and from the distributed network are monitored.

Based on the foregoing, it can be seen that the present invention provides systems and methods for deploying protection agents to devices connected to a distributed network. Those skilled in the art will appreciate that the methods of the present invention can be embodied as computer-executable instructions stored on computer-readable media and can be implemented using programming techniques and/or functions other than those specifically described herein. Many other modifications, features and embodiments of the present invention will become evident to those of skill in the art. Furthermore, certain terminology used herein, such as the terms “network device,” “inter-network communication,” etc., was chosen for ease of reference and is used by way of general illustration and not limitation.

It should also be appreciated, therefore, that many aspects of the present invention were described above by way of example only and are not intended as required or essential elements of the invention unless explicitly stated otherwise. Accordingly, it should be understood that the foregoing relates only to certain exemplary embodiments of the invention and that numerous changes may be made thereto without departing from the spirit and scope of the invention as defined by the following claims. It should be further understood that the invention is not restricted to the illustrated embodiments and that various other modifications can be made within the scope of the following claims. 

What is claimed is:
 1. A method for intrusion prevention, the method comprising the steps of: an intrusion prevention device, comprising a computer, receiving from a client computing device at multiple successive times, re-registration information for a program agent installed on the client computing device to detect malicious intrusion, the re-registration information notifying the intrusion prevention device that the program agent is still installed on the client computing device; subsequently, the intrusion prevention device detecting a request sent by the client computing device addressed to a remote web server for a web page, and in response, the intrusion prevention device determining, whether the client computing device has re-registered the program agent within a predetermined time interval from a time of the request; and if so, the intrusion prevention device propagating the request to the web server, and if not, the intrusion prevention device: blocking the request so it cannot be sent to the web server, and if the program agent is not installed on the client computing device, and delivering the program agent to detect malicious intrusions to the client computing device for installation at the client computing device without a request by the client computing device to receive the program agent.
 2. The method of claim 1, wherein the intrusion prevention device detects the request sent by the client computing device to the web server by detecting message traffic employing HTTP or HTTPS protocols generated by the client computing device.
 3. The method of claim 1, wherein the intrusion prevention device detects the request sent by the client computing device to the web server by detecting message traffic on one or more of network port 80 and network port 443 generated by the client computing device.
 4. The method of claim 1, wherein the intrusion prevention device periodically receives the re-registration information from the program agent installed on the client computing device.
 5. The method of claim 1, wherein determining the client computing device has re-registered the program agent to detect malicious intrusions within a predetermined time interval further comprises determining whether no information corresponding to the client computing device has been stored.
 6. The method of claim 1, wherein the intrusion prevention device requests delivery of the program agent to detect malicious intrusions to the client computing device for installation at the client computing device by requesting the client computing device to download and install the program agent, and sending a hyperlink to the client computing device that, when activated, initiates the download of the program agent to detect malicious intrusion.
 7. The method of claim 1, wherein the client computing device is selected from a group consisting of a client and a server.
 8. The method of claim 1, wherein the step of blocking the request so it cannot be sent to the web server does not block other requests sent by the client computing device to other web servers such that the other requests sent by the client computing device to the other web servers are permitted despite the blocking of the request sent to the first said web server.
 9. The method of claim 1, wherein allowing the communication with the other web server is contingent on the program agent being re-registered within a predetermined time interval.
 10. The method of claim 1, further comprising: the intrusion prevention device receiving, from the client computing device, initial registration information for the program agent responsive to initial installation of the program agent in the client computing device; and the intrusion prevention device receiving, from the client computing device, the re-registration information subsequent to receipt of the initial registration information, wherein the intrusion prevention device propagates the request from the client computing device to the web server based on the re-registration information.
 11. A method for intrusion prevention, the method comprising the steps of: an intrusion prevention device, comprising a computer, receiving from an external device, comprising another computer, of a distributed network at multiple successive times, re-registration information for a program agent installed on the external device to detect malicious intrusion, the re-registration information notifying the intrusion prevention device that the program agent is still installed on the external device; subsequently, the intrusion prevention device detecting a request sent by the external device to establish a virtual private network communication session with a device that is internal to the distributed network, and in response, the intrusion prevention device determining whether the external device has re-registered the program agent to detect malicious intrusions within a predetermined time interval from a time of the request; and if so, the intrusion prevention device allowing the external device to establish the virtual private network session communication, and if not, the intrusion prevention device: blocking the request so that the virtual private network communication session cannot be established and if the program agent is not installed on the external device, and delivering the program agent to detect malicious intrusions to the external device for installation at the external device without a request by the external device to receive the program agent.
 12. The method of claim 11, wherein the intrusion prevention device periodically receives and stores re-registration information generated by program agents installed on the external device.
 13. The method of claim 11, wherein determining whether the external device has re-registered the program agent within a pre-determined time interval comprises determining whether no re-registration information corresponding to the external device has been stored.
 14. The method of claim 11, wherein the intrusion prevention device requests delivery of the program agent to detect malicious intrusions to the external device for installation at the external device by requesting the external device to download and install the program agent; and sending a hyperlink to the external device that, when activated, initiates the download of the program agent to detect malicious intrusion.
 15. The method of claim 11, wherein the step of blocking the request to the device internal to the distributed network so it cannot be sent to the device that is internal to the distributed network respective to a first activity does not block other requests sent by the external device respective to a second activity such that the requests sent by the external device to the other device internal respective to the second activity are permitted despite the blocking of the request respective to the first activity.
 16. The method of claim 11, wherein allowing the other virtual private network communication session is contingent on the program agent being re-registered within a predetermined time interval.
 17. The method of claim 11: the intrusion prevention device receiving, from the external device, initial registration information for the program agent responsive to initial installation of the program agent in the external device; and the intrusion prevention device receiving, from the external device, the re-registration information subsequent to receipt of the initial registration information, wherein the intrusion prevention device propagates the request from the external device to the device internal to the distributed network based on the re-registration information. 